Most likely causes:

• The "Scripts" or "Scripts and Executables" flag is not configured in Rights and Permissions at the server, site, application, or page level.
• The configuration/system.webServer/handlers@accessPolicy attribute does not have Script or Execute configured.
• Execute access is denied when you try to run a CGI file or other executable.
• Script access is denied when you try to access an ASP, ASP.NET or other dynamic scripting file.
• The script mapping for the file you are trying to run is not configured to recognize the HTTP verb you are using (such as GET or POST).
• The HTTP verb for the script mapping is case sensitive, and use upper case. The HTTP verb "POST" is correct, while "post" is incorrect and execution is denied.

Things you can try:

• Enable scripts to run for the requested resource.
  1. Open IIS Manager and navigate to the level you want to manage.
  2. On the Features page, double-click the Handler Mappings feature.
  3. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions.
  4. In the Edit Handler Mappings dialog box, select Scripts to enable handlers that require script rights.
• Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level.
• Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase.
• Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

More Information:

View more information »

Microsoft Knowledge Base Articles:

• 318380